Skip to content

ci(release): add tag-triggered PyPI publishing workflow - #234

Merged
lzsweb merged 2 commits into
mainfrom
dev/release-workflow
Nov 13, 2026
Merged

lzsweb merged 2 commits into
mainfrom
dev/release-workflow

Conversation

@lzsweb

@lzsweb lzsweb commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Add .github/workflows/release.yml: v* tag → validate (main ancestor + version match) → python -m build + twine check → PyPI trusted publishing → draft GitHub Release
  • Add .github/release-template.md: release notes skeleton rendered via string.Template.safe_substitute (TAG_NAME / VERSION / FULL_CHANGELOG_URL)
  • Bump version to 2.1.0rc1 for pre-release pipeline verification

Workflow jobs

Job Gate What it does
validate — Tag commit must be on main; dashscope/version.py must match tag
package validate Build wheel + sdist, twine check, upload only *.whl / *.tar.gz
pypi package Trusted publishing via OIDC, environment pypi (manual approval)
release package Render template, auto-detect pre-release (rc/a/b/dev), create draft GitHub Release

Prerequisites before tagging

  1. Merge this PR to main
  2. Configure PyPI trusted publisher: owner dashscope, repo dashscope-sdk-python, workflow release.yml, environment pypi
  3. git tag -a v2.1.0rc1 -m "2.1.0rc1" && git push origin v2.1.0rc1
  4. Approve pypi environment in Actions
  5. Verify pip install dashscope==2.1.0rc1

Supersedes #233 (which carried unrelated AgenticX migration commits).

zhansheng.lzs added 2 commits November 13, 2026 11:19
Add .github/workflows/release.yml: v* tag → validate (main ancestor +
version match) → build + twine check → PyPI trusted publishing →
draft GitHub Release with rendered release-template.md.

Bump version to 2.1.0rc1 for pre-release pipeline verification.
The legacy 1.x test suite targets a single runtime; running it across
the full 3.9–3.13 matrix wastes CI minutes without adding coverage.
@lzsweb
lzsweb merged commit e644790 into main Nov 13, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant